Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 75

reference
58
name
Article 4 - No 75
article-4-direction
58
permitted-development-rights

undefined

Minor alterations in Conservation Areas
uprns
address-texts
geometry
MULTIPOLYGON (((-0.202390 51.498410,-0.202350 51.498420,-0.202410 51.498500,-0.202490 51.498580,-0.202480 51.498590,-0.202500 51.498600,-0.202560 51.498580,-0.202570 51.498570,-0.202570 51.498550,-0.202430 51.498400,-0.202390 51.498410)),((-0.201810 51.498680,-0.201680 51.498720,-0.201640 51.498740,-0.201660 51.498760,-0.201670 51.498760,-0.201670 51.498770,-0.201950 51.498760,-0.201870 51.498660,-0.201810 51.498680)),((-0.203570 51.497940,-0.203240 51.498050,-0.203290 51.498110,-0.203430 51.498250,-0.203470 51.498250,-0.203470 51.498240,-0.204060 51.498030,-0.204060 51.498010,-0.203890 51.497820,-0.203570 51.497940)),((-0.202810 51.498200,-0.202530 51.498300,-0.202510 51.498310,-0.202510 51.498320,-0.202500 51.498320,-0.202500 51.498330,-0.202680 51.498520,-0.202730 51.498520,-0.202850 51.498470,-0.203310 51.498310,-0.203320 51.498300,-0.203320 51.498280,-0.203140 51.498090,-0.202810 51.498200)))
point
POINT (-0.203163 51.49822)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your dataset is missing the permitted-development-rights column.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL